projects / gtk4.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 6f73a75) | patch
events: Use GdkDrop as event sequence
authorBenjamin Otte <otte@redhat.com>
Wed, 19 Feb 2020 03:43:03 +0000 (04:43 +0100)
committerBenjamin Otte <otte@redhat.com>
Sat, 22 Feb 2020 06:33:40 +0000 (07:33 +0100)
commitbe4b34aa8f6b300d611081c8b2cdae41fecf8c43
treec216b270a12c26a08c0a8f7c00f6a376a39d3d60tree | snapshot
parent6f73a750a7ae1ee105a6b24a71033b6e3f05318bcommit | diff
events: Use GdkDrop as event sequence

This allows treating drop events like touch events, which GTK groups by
event sequence.

It's a bit ugly that we just case the GdkDrop pointer, but event
sequences are only meant to be unique pointer ids, so it's fine.
gdk/gdkevents.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.